Open
Conversation
This was referenced Jan 2, 2026
I believe this also enables something like this from #80 (comment), although in a bit roundabout way ^^' Resulting in: But I haven't tested it yet, just judging from an example. To quote from the same issue:
|
|
Or even something like that, from the same issue? -creature-genus = { $creature ->
[elf] Maskulinum
[fairy] Femininum
*[other] ??
}
-creature-akkusative = { $creature ->
[fairy] Fee
[elf] Elfen
}
you-see =
Du siehst { -creature-genus(creature: $object) ->
*[Maskulinum] einen { -creature-akkusative(creature: $object) }
[Femininum] eine { -creature-akkusative(creature: $object) }
[Neutrum] ein { -creature-akkusative(creature: $object) }
}.Even if the original version is prettier, because you can pack everything together. I guess you can do it with selectors, too? -creature-db = { $creature ->
[elf] { $attr -> {
[singular] Elf
[plural] Elfen
[nominativ] Elf
[akkusativ] Elfen
[genus] Maskulinum
*[other] ??
}
[fairy] { $attr -> {
[singular] Fee
[plural] Feen
[nominativ] Fee
[akkusativ] Fee
[genus] Femininum
*[other] ??
}
}
you-see =
Du siehst { -creature-db(creature: $object, attr: "genus") ->
*[Maskulinum] einen { -creature-db(creature: $object, attr: "akkusativ" }
[Femininum] eine { -creature-db(creature: $object, attr: "akkusativ" }
[Neutrum] ein { -creature-db(creature: $object, attr: "akkusativ" }
}. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This proposed syntax change would require the release of a new Fluent version, probably 1.1. It's forwards-incompatible, i.e. while all Fluent 1.0 content is valid Fluent 1.1, not all Fluent 1.1 content would be considered valid by a Fluent 1.0 processor.
Effectively, this would allow for usage like:
Not all inline expression values are supported as named arguments, so e.g.
{ -term(foo: -bar) }would continue to be a syntax error. My sense is that the strong, active desire is only for variable references, and that other uses are much more limited.I'll be sumitting PRs for fluent.js and python-fluent to showcase the impact on implementations. From #325 I gather that fluent-rs might already support this, or that it's likely to be relatively straightforward to add there.
We'll need to consider carefully how to handle this in Pontoon, as we may need a per-project configuration of the supported Fluent version, or we need a solution for #208.
In Firefox, we'll need to review the capabilities of the fluent-rs version we're using.